Skip to content

[github] Reporting a bug

Jump to bottom
Infernio edited this page Jul 23, 2022 · 43 revisions

IMPORTANT: Before posting an issue, be sure to ask at the official thread (linked under Questions & Feedback on our front page readme); maybe the bug is already fixed in some development version or you are doing something wrong. Post an issue on github ONLY after doing so and then making sure the bug is not already on the bug tracker by searching on the key elements of your problem. See the GitHub Searching issues article for more ideas.

Posting issues guidelines

When asking for help (initially at the official forums thread linked to above) please provide all of the following info:

  • Bug description - be sure to include:

    • what you did (step-by-step),
    • what you expected, and
    • what happened.

  • Any and every error message you encounter: please produce the BashBugDump.log (see the section below). Failing to do so will hinder debugging - post at least the contents of any stdout/stderr window that pops up with errors (python tracebacks).

  • Are you using a bash.ini ? If so, include its contents (in spoiler tags, please!).

  • Is the problem related to the Bashed Patch ? If so include the following (while on the Mods tab):

    • Your Load Order (in spoiler tags). 'View' > 'List Mods...'.
    • Your Bashed Tags (in spoiler tags). 'View' > 'List Bash Tags...'.
    • Your Bashed Patch config (in spoiler tags). Right click on the Bashed Patch > 'List Patch Config...'.

To increase your chances your BP bug is fixed (to a number greater than 0) be sure to supply the minimal load order and patch options that reproduce your bug. That is, deselect all batch patch options and deactivate all the mods then try to pin down which options and which mods trigger the bug.

The rest of the info we need is also contained in BashBugDump.log. In particular we need to know:

  • Your operating system! If on Windows Vista or later and the game is in the default directory (ex: C:\Program Files (x86)\Bethesda Softworks\Oblivion), please install it somewhere else (like C:\Games\Oblivion). This can cause lots of problems, due to UAC (User Account Control).

  • Wrye Bash version! Also specify if you are using Python Wrye Bash, or Standalone Wrye Bash exe ( WBSA ). If you're using a development version, be sure to include the commit SHA.

The BashBugDump.log

The BashBugDump.log contains precious information on your python install, encodings etc - you must add this to your report.

In previous versions, you had to use a command line switch to enter debug mode. Since Wrye Bash 310, this is no longer necessary. The file will always be generated, no matter what.

Retrieving the log file

The BashBugDump.log is a text file (loads into Windows Notepad), and the contents can be pasted into forum posts (Please use "spoiler tags").

If you're using the Installer version, BashBugDump.log will be in the game's Mopy folder (e.g. G:\steam\steamapps\common\Skyrim\Mopy). Otherwise, it will be in the Mopy folder from which you launched Wrye Bash.

Clone this wiki locally